Triple
T14260883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orange tree courtyard |
E353512
|
entity |
| Predicate | functionDuringMarketEra |
P113475
|
FINISHED |
| Object | meeting place for merchants |
—
|
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: meeting place for merchants | Statement: [orange tree courtyard, functionDuringMarketEra, meeting place for merchants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringMarketEra Context triple: [orange tree courtyard, functionDuringMarketEra, meeting place for merchants]
-
A.
functionDuringReconstructionEra
Indicates that an entity performs or holds a particular function, role, or activity specifically during the Reconstruction Era.
-
B.
functionDuringEdoPeriod
Indicates that the function, role, or activity occurred specifically during Japan’s Edo period.
-
C.
functionDuringImperialEra
Indicates that a function, role, or activity occurred or was in effect during the imperial era.
-
D.
functionDuringBonnCapitalEra
Indicates that a function, role, or activity occurred during the historical period when Bonn served as the capital.
-
E.
marketHeldOn
Indicates that a market event takes place at a specific time and/or location.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de635534988190816fdfb315cd2a3f |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:09 a.m.