Triple
T1490369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SoftQuad Software |
E29562
|
entity |
| Predicate | roleInStandards |
P28582
|
FINISHED |
| Object | helped shape early web publishing practices |
—
|
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: helped shape early web publishing practices | Statement: [SoftQuad Software, roleInStandards, helped shape early web publishing practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInStandards Context triple: [SoftQuad Software, roleInStandards, helped shape early web publishing practices]
-
A.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInEcosystem
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
D.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
E.
coPublishesStandardsWith
Indicates that two or more entities jointly develop and issue formal standards or specifications together.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c233ec819087e1233af02aabfc |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52c703c8190a56389b09d97659f |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:12 p.m.