Triple
T26955930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Blue |
E678902
|
entity |
| Predicate | currentWhereabouts |
P145498
|
FINISHED |
| Object | unknown as original stone |
—
|
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: unknown as original stone | Statement: [French Blue, currentWhereabouts, unknown as original stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentWhereabouts Context triple: [French Blue, currentWhereabouts, unknown as original stone]
-
A.
currentlyLocatedAt
chosen
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
B.
currentLocationType
Indicates the type or category of place where an entity is currently located.
-
C.
presentDayLocationCorrespondsTo
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
-
D.
locationDuringUse
Indicates the place or spatial context where an entity is situated specifically while it is being used or in active operation.
-
E.
currentLocationSince
Indicates the point in time since which an entity has been at its current location.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 27, 2026, 6:27 a.m.