Triple
T27153759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frenchman William Fuquay |
E682461
|
entity |
| Predicate | propertyContained |
P164492
|
FINISHED |
| Object | mineral spring |
—
|
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: mineral spring | Statement: [Frenchman William Fuquay, propertyContained, mineral spring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyContained Context triple: [Frenchman William Fuquay, propertyContained, mineral spring]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
isContributingPropertyTo
Indicates that one property plays a role in producing, influencing, or determining another property or overall outcome.
-
C.
believedToContain
Indicates that something is thought or assumed to hold, include, or possess something else, without certainty.
-
D.
hasContainment
Indicates that one entity spatially or logically encloses, includes, or holds another within its bounds.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 9:15 a.m.