Triple
T29354006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toro |
E744387
|
entity |
| Predicate | hasRoyalPalaceIn |
P11479
|
FINISHED |
| Object | Fort Portal |
E1072399
|
NE 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: Fort Portal | Statement: [Toro, hasRoyalPalaceIn, Fort Portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalPalaceIn Context triple: [Toro, hasRoyalPalaceIn, Fort Portal]
-
A.
hasMunicipalPalaceIn
Indicates that a municipality possesses or is associated with a municipal palace located in the specified place.
-
B.
palaceLocatedIn
Indicates that a palace is situated within or belongs to a specific geographic or administrative location.
-
C.
containsRoyalResidence
chosen
Indicates that a location includes or encompasses a residence used by royalty.
-
D.
servedRoyalResidence
Indicates that an entity functioned as an official residence used by royalty.
-
E.
palace
Indicates that an entity is a palace, i.e., a grand official residence typically used by royalty or high-ranking authorities.
- F. None of above.
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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25d90d8af88190a141b061c6d835f9 |
completed | June 7, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 2:09 p.m.