Triple
T38005559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epanterias |
E948224
|
entity |
| Predicate | likelyRepresents |
P189957
|
FINISHED |
| Object | large specimen of Allosaurus |
—
|
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: large specimen of Allosaurus | Statement: [Epanterias, likelyRepresents, large specimen of Allosaurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyRepresents Context triple: [Epanterias, likelyRepresents, large specimen of Allosaurus]
-
A.
likelyIndicates
Indicates that one fact, observation, or condition serves as probabilistic evidence suggesting, but not guaranteeing, the presence or truth of another.
-
B.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
-
C.
likelyUse
Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
-
D.
likelyStatus
Indicates the probable or expected state or condition of an entity based on available information or inference.
-
E.
likelyDistribution
Indicates that one entity is the probable or expected distribution pattern, allocation, or spread associated with 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.