Triple
T35702841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Barn |
E1031633
|
entity |
| Predicate | hasPossibleNameOrigin |
P135098
|
FINISHED |
| Object | distinctive barn-like facility |
—
|
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: distinctive barn-like facility | Statement: [The Barn, hasPossibleNameOrigin, distinctive barn-like facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleNameOrigin Context triple: [The Barn, hasPossibleNameOrigin, distinctive barn-like facility]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
C.
hasUncertainOriginalName
Indicates that the entity’s original name is not known with certainty or is subject to doubt or ambiguity.
-
D.
hasPossibleEthnicOriginOfSurname
Indicates that a surname is associated with, or can plausibly originate from, a particular ethnic group or ethnicity.
-
E.
hasLikelyOrigin
chosen
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 3, 2026, 4:05 p.m.