Triple
T35618160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/TC 68/SC 4 |
E1029230
|
entity |
| Predicate | subcommitteeNumber |
P183460
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [ISO/TC 68/SC 4, subcommitteeNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subcommitteeNumber Context triple: [ISO/TC 68/SC 4, subcommitteeNumber, 4]
-
A.
hasNumberOfSubcommittees
Indicates the relationship that specifies how many subcommittees are associated with a given entity.
-
B.
hadSubcommittee
Indicates that an entity (typically an organization or committee) possessed or was associated with a subordinate committee or subcommittee.
-
C.
committeeNumber
Indicates the specific numerical identifier assigned to a committee in a given context or system.
-
D.
hasSubcommitteeRoleIn
Indicates that an entity holds a specific role or position within a particular subcommittee.
-
E.
typeOfAppropriationsSubcommittee
Indicates that one entity is a specific type or category of an appropriations subcommittee in relation to another entity.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.