Triple
T1885164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBE |
E39946
|
entity |
| Predicate | orderFoundedOn |
P13880
|
FINISHED |
| Object | 4 June 1917 |
—
|
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: 4 June 1917 | Statement: [GBE, orderFoundedOn, 4 June 1917]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderFoundedOn Context triple: [GBE, orderFoundedOn, 4 June 1917]
-
A.
orderFoundedFrom
Indicates that an order was initiated or created as a result of, or originating from, a specific source or prior entity.
-
B.
orderFounded
chosen
Indicates that an organization or group was established or created at a specific time or by a specific entity.
-
C.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or entity.
-
D.
orderFoundedIn
Indicates the place or location where an order (such as a religious, military, or organizational order) was originally established or founded.
-
E.
orderEstablished
Indicates that a formal sequence or arrangement between entities has been created and set as the authoritative or agreed-upon order.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb4f53f408190ae30e1a12721e7d7 |
completed | March 7, 2026, 5:17 a.m. |
| PD | Predicate disambiguation | batch_69abafe497a88190a1da6af2888b71b4 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.