Triple
T30364069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIX 98 |
E772366
|
entity |
| Predicate | conformanceMark |
P162411
|
FINISHED |
| Object | UNIX 98 Brand |
—
|
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: UNIX 98 Brand | Statement: [UNIX 98, conformanceMark, UNIX 98 Brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conformanceMark Context triple: [UNIX 98, conformanceMark, UNIX 98 Brand]
-
A.
conformanceType
Indicates the specific manner or degree to which one entity adheres to, complies with, or satisfies the requirements, rules, or expectations defined by another.
-
B.
conformanceStyle
Indicates the specific manner, pattern, or set of rules by which something adheres to or complies with a given standard or specification.
-
C.
conformanceMechanism
Indicates the method, process, or mechanism by which something complies with or adheres to a specified standard, rule, or requirement.
-
D.
isMarkedAccordingTo
chosen
Indicates that one entity bears marks, labels, or annotations that conform to the rules, standards, or criteria specified by another entity or reference.
-
E.
usesConformanceLevels
Indicates that one entity applies or adheres to defined conformance levels when interacting with or evaluating 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6827ecae8819092c15bbb1529dbad |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:58 p.m.