Triple
T24832964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LMP3 |
E621388
|
entity |
| Predicate | positionInPrototypeHierarchy |
P5163
|
FINISHED |
| Object | below Hypercar |
—
|
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: below Hypercar | Statement: [LMP3, positionInPrototypeHierarchy, below Hypercar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInPrototypeHierarchy Context triple: [LMP3, positionInPrototypeHierarchy, below Hypercar]
-
A.
positionInHierarchy
chosen
Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
-
B.
positionInCascade
Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
-
C.
isPrototypeOfClassUsedIn
Indicates that one class serves as the prototype or template for another class that is used within a given context or system.
-
D.
hasPrototype
Indicates that an entity is based on, derived from, or exemplified by a specific prototype.
-
E.
positionInFamilyTree
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:16 a.m.