Triple
T36715841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of Venezuela |
E906909
|
entity |
| Predicate | firstRaised |
P146377
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Flag of Venezuela, firstRaised, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRaised Context triple: [Flag of Venezuela, firstRaised, early 19th century]
-
A.
firstRaisedIn
Indicates the context (such as time, place, or source) in which an issue, idea, or topic was initially brought up or introduced.
-
B.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
-
C.
firstRaisedBy
Indicates that one entity was the earliest or original source to bring up, introduce, or initiate the referenced issue, idea, or topic in relation to another entity.
-
D.
firstRaisedOnBuilding
chosen
Indicates that something (such as a flag, banner, or symbol) was initially hoisted or displayed on a particular building.
-
E.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
- F. None of above.
Provenance (3 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.