Triple
T868628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 9660 |
E18760
|
entity |
| Predicate | supportsTimestamps |
P20333
|
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: [ISO 9660, supportsTimestamps, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimestamps Context triple: [ISO 9660, supportsTimestamps, true]
-
A.
supportsTimescale
Indicates that one entity is capable of operating with, accommodating, or being compatible with a specified timescale or range of temporal resolutions.
-
B.
associatedWithTime
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
C.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
timeOfAttestation
Indicates the specific time at which a statement, document, or claim is formally attested or verified.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.