Triple
T15640969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman numeral system |
E376061
|
entity |
| Predicate | isNonPositional |
P119568
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Roman numeral system, isNonPositional, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonPositional Context triple: [Roman numeral system, isNonPositional, true]
-
A.
isNonPositionalSince
Indicates that something has not depended on or been defined by positional context since a specified point in time.
-
B.
hasPositionalCategory
Indicates that something is associated with a specific positional classification or category based on its location or arrangement.
-
C.
isNonBinding
Indicates that the relationship or agreement exists but does not create any legally or formally enforceable obligation between the involved entities.
-
D.
isNonlocal
Indicates that the relationship or effect occurs between entities separated in space (or context) without requiring direct, local interaction.
-
E.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed06b388190bfebb77fe70e7df1 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.