Triple
T15343456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herrerasauria |
E366855
|
entity |
| Predicate | debatedPlacement |
P57127
|
FINISHED |
| Object | basal theropods |
—
|
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: basal theropods | Statement: [Herrerasauria, debatedPlacement, basal theropods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debatedPlacement Context triple: [Herrerasauria, debatedPlacement, basal theropods]
-
A.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
-
B.
debatedWithin
chosen
Indicates that something is discussed or argued about within a particular group, context, or domain.
-
C.
debatedBetween
Indicates a situation in which two or more parties engage in a discussion or argument over differing views about a particular issue or topic.
-
D.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
E.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e163a3c8190ab933411372c1573 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.