Triple
T868626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 9660 |
E18760
|
entity |
| Predicate | dataOrganization |
P4786
|
FINISHED |
| Object | sectors and logical blocks |
—
|
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: sectors and logical blocks | Statement: [ISO 9660, dataOrganization, sectors and logical blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataOrganization Context triple: [ISO 9660, dataOrganization, sectors and logical blocks]
-
A.
massOrganization
Indicates a relationship where an organization is characterized as a mass organization, typically involving broad-based, large-scale membership or participation.
-
B.
organizedAs
chosen
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
C.
controlledOrganization
Indicates that one entity has the authority to direct, manage, or significantly influence the operations and decisions of another organization.
-
D.
organizes
Indicates that one entity arranges, coordinates, or structures activities, items, or people into an ordered or planned form for a particular purpose.
-
E.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
- 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_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. |
Created at: March 1, 2026, 7:39 p.m.