Triple
T38608907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Flagstones (pilot concept) |
E934419
|
entity |
| Predicate | hasWorkingTitleRelatedTo |
P64794
|
FINISHED |
| Object | The Flagstones |
—
|
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: The Flagstones | Statement: [The Flagstones (pilot concept), hasWorkingTitleRelatedTo, The Flagstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkingTitleRelatedTo Context triple: [The Flagstones (pilot concept), hasWorkingTitleRelatedTo, The Flagstones]
-
A.
hasWorkingTitle
chosen
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
B.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
C.
hasWorkingTitleStatus
Indicates that an entity currently holds the status of having a provisional or working title rather than a finalized official title.
-
D.
hasWorkTitleType
Indicates that an entity holds a specific category or type of work-related title (e.g., job title type or role classification).
-
E.
hasWorkTitleSource
Indicates that the source or origin of an entity’s work title is specified or referenced.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: May 3, 2026, 4:32 p.m.