Triple
T27917571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allosauroidea |
E706114
|
entity |
| Predicate | containsIconicMember |
P7638
|
FINISHED |
| Object | Allosaurus fragilis |
—
|
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: Allosaurus fragilis | Statement: [Allosauroidea, containsIconicMember, Allosaurus fragilis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsIconicMember Context triple: [Allosauroidea, containsIconicMember, Allosaurus fragilis]
-
A.
hasMembersWith
Indicates that a group or collection includes one or more specific members that satisfy a given condition or characteristic.
-
B.
hasMembers
chosen
Indicates that a group, organization, or collection includes certain entities as its members.
-
C.
hasCoreMember
Indicates that an entity includes another entity as a central or primary member of its group, organization, or structure.
-
D.
includeMember
Indicates that one entity contains or has another entity as a member or part of its composition.
-
E.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 27, 2026, 6:54 p.m.