Triple
T2074064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate of Jamaica |
E44880
|
entity |
| Predicate | termRelationTo |
P34778
|
FINISHED |
| Object | life of the Parliament |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: life of the Parliament | Statement: [Senate of Jamaica, termRelationTo, life of the Parliament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termRelationTo Context triple: [Senate of Jamaica, termRelationTo, life of the Parliament]
-
A.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
B.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
C.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
E.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba101c008190840763d2f28fa8d7 |
completed | March 7, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69abb7b0edac8190a58eabee55f73deb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:41 p.m.