Triple
T27616064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQuaRE |
E700440
|
entity |
| Predicate | standardFamilyIncludes |
P66287
|
FINISHED |
| Object | ISO/IEC 25000 |
—
|
NE NERFINISHED |
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: ISO/IEC 25000 | Statement: [SQuaRE, standardFamilyIncludes, ISO/IEC 25000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardFamilyIncludes Context triple: [SQuaRE, standardFamilyIncludes, ISO/IEC 25000]
-
A.
familyIncluded
Indicates that one entity’s family members are included within the scope, coverage, or membership defined by the other entity.
-
B.
standardFamilyOf
chosen
Indicates that one entity is the canonical or commonly accepted family grouping or classification associated with another entity.
-
C.
servesFamily
Indicates that an entity provides food, services, or accommodations suitable for families, typically welcoming and catering to family groups.
-
D.
featuresFamily
Indicates that something includes, presents, or highlights a family as a central element or subject.
-
E.
worksForFamily
Indicates that one entity is employed by or performs work on behalf of another entity that is a family member or family unit.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 2:12 p.m.