Triple
T33944766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemonum |
E870259
|
entity |
| Predicate | knownAsInFrench |
P6538
|
FINISHED |
| Object | Poitiers (site) |
—
|
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: Poitiers (site) | Statement: [Lemonum, knownAsInFrench, Poitiers (site)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAsInFrench Context triple: [Lemonum, knownAsInFrench, Poitiers (site)]
-
A.
nameInFrench
chosen
Indicates that an entity is known or referred to by a specific name expressed in the French language.
-
B.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
-
C.
knownAsInCanada
Indicates that an entity is referred to or recognized by a particular name specifically within the context of Canada.
-
D.
knownAsInThai
Indicates that an entity is referred to by a specific name or term in the Thai language.
-
E.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:49 a.m.