Triple
T1869646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON |
E39004
|
entity |
| Predicate | isHumanReadable |
P5371
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [JSON, isHumanReadable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHumanReadable Context triple: [JSON, isHumanReadable, true]
-
A.
humanReadable
chosen
Indicates that something is expressed in a form that is easily understandable or interpretable by humans.
-
B.
isHuman
Indicates that the subject entity possesses the defining characteristics or status of being a human.
-
C.
usedInHumanReadableContexts
Indicates that something is employed or appears in contexts intended to be easily understood by humans, rather than in machine-oriented or technical formats.
-
D.
machineReadable
Indicates that something is in a format that can be automatically processed or interpreted by a computer without human intervention.
-
E.
usedInMachineReadableContexts
Indicates that something is employed or applied within formats or environments that can be automatically processed and interpreted by machines.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.