Triple
T22955119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC JTC 1/SC 32 |
E570732
|
entity |
| Predicate | areaOfWG3 |
P58897
|
FINISHED |
| Object | database languages |
—
|
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: database languages | Statement: [ISO/IEC JTC 1/SC 32, areaOfWG3, database languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfWG3 Context triple: [ISO/IEC JTC 1/SC 32, areaOfWG3, database languages]
-
A.
coreAreaOf
chosen
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
B.
workingGroup
Indicates that multiple entities collaborate as a designated team or committee to work together toward a shared task, project, or objective.
-
C.
relatedWorkingGroup
Indicates that there is an associated or connected working group that is relevant to or involved with the referenced entity or activity.
-
D.
collaborationArea
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
E.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f09de48190b55913570c965412 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.