Triple
T32582765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Order of the Lion |
E832833
|
entity |
| Predicate | laterLinkedTo |
P60493
|
FINISHED |
| Object | Belgian Congo |
—
|
NE NERFINISHED |
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: Belgian Congo | Statement: [Royal Order of the Lion, laterLinkedTo, Belgian Congo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLinkedTo Context triple: [Royal Order of the Lion, laterLinkedTo, Belgian Congo]
-
A.
currentlyLinkedTo
Indicates that one entity is at this moment connected or associated with another entity in an ongoing relationship or linkage.
-
B.
laterRelationWith
chosen
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
C.
hasBeenLinkedTo
Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
-
D.
linkedToDate
Indicates that an entity is associated or connected to a specific date or point in time.
-
E.
canBeLinkedTo
Indicates that one entity has the potential or capability to be connected or associated with another entity.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:04 a.m.