Triple
T1160241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheme |
E24474
|
entity |
| Predicate | macroSystemType |
P15304
|
FINISHED |
| Object | hygienic macro system |
—
|
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: hygienic macro system | Statement: [Scheme, macroSystemType, hygienic macro system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: macroSystemType Context triple: [Scheme, macroSystemType, hygienic macro system]
-
A.
systemType
chosen
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
C.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
D.
packageSystem
Indicates a relationship where an item or component is organized, bundled, or managed within a particular packaging or distribution system.
-
E.
currentSystem
Indicates that an entity is the system or configuration that is presently active or in use.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.