Triple
T38102704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stegosauria |
E951427
|
entity |
| Predicate | containsFamousMember |
P304
|
FINISHED |
| Object | Stegosaurus |
E281543
|
NE 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: Stegosaurus | Statement: [Stegosauria, containsFamousMember, Stegosaurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFamousMember Context triple: [Stegosauria, containsFamousMember, Stegosaurus]
-
A.
famousMember
Indicates that an entity is a well-known or widely recognized member of a particular group, organization, or category.
-
B.
hasNotableMember
chosen
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
C.
hasFamousSection
Indicates that an entity includes or contains a part, area, or segment that is widely recognized or renowned.
-
D.
hasFictionalMember
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
E.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
- F. None of above.
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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01e4ba62748190a4756689219b6269 |
completed | May 11, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7cfc2a88190b866e951f9351610 |
completed | June 28, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_6a01e3fc2d908190a075c7c1549e5640 |
completed | May 11, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:21 p.m.