Triple
T27192505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Step I |
E683511
|
entity |
| Predicate | coreVersionOf |
P162243
|
FINISHED |
| Object | Myers–Briggs Type Indicator |
—
|
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: Myers–Briggs Type Indicator | Statement: [Step I, coreVersionOf, Myers–Briggs Type Indicator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVersionOf Context triple: [Step I, coreVersionOf, Myers–Briggs Type Indicator]
-
A.
exportVersionOf
Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
-
B.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
C.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
-
D.
latestCoreVersion
Indicates that one entity specifies or identifies the most recent or up-to-date core version associated with another entity.
-
E.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
- 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_69eefad140408190b8586fdebcf9af46 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625ac8e4c8190b44c30995739731f |
completed | May 2, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:32 a.m.