Triple
T13069792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F36 |
E329425
|
entity |
| Predicate | hasModelCode |
P2390
|
FINISHED |
| Object | F36 |
—
|
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: F36 | Statement: [F36, hasModelCode, F36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModelCode Context triple: [F36, hasModelCode, F36]
-
A.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
B.
hasModelLine
Indicates that an item, product, or entity belongs to or is associated with a particular model line or series.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasModelType
chosen
Indicates that an entity is associated with or classified under a specific model type.
-
E.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ee6130819095d835e7ff6a8c5b |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.