Triple
T10729053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concept Script |
E253024
|
entity |
| Predicate | hasLogicalSystemType |
P48245
|
FINISHED |
| Object | second-order logic |
—
|
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: second-order logic | Statement: [Concept Script, hasLogicalSystemType, second-order logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLogicalSystemType Context triple: [Concept Script, hasLogicalSystemType, second-order logic]
-
A.
hasLogicalIdentifier
Indicates that an entity is associated with a specific logical identifier used to uniquely reference or distinguish it within an information or data model.
-
B.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
C.
belongsToSystemType
Indicates that one entity is classified under, or is a member of, a particular system type.
-
D.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
E.
hasLogicalStructure
chosen
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70fc92a18819089cc67afee1c9b96 |
completed | April 9, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f309a44881908e49e3ba478c35b4 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:14 p.m.