Triple
T27492941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartwright |
E693940
|
entity |
| Predicate | originallyIndicated |
P195630
|
FINISHED |
| Object | person who built carts |
—
|
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: person who built carts | Statement: [Cartwright, originallyIndicated, person who built carts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyIndicated Context triple: [Cartwright, originallyIndicated, person who built carts]
-
A.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
B.
originallyHad
Indicates that an entity previously possessed, contained, or was associated with something before a change, loss, or transformation occurred.
-
C.
wasOriginally
Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
-
D.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
-
E.
originallyPresentedAs
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 27, 2026, 1:06 p.m.