Triple
T11748871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Number 30 |
E279353
|
entity |
| Predicate | isLargeScale |
P60650
|
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: [Number 30, isLargeScale, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargeScale Context triple: [Number 30, isLargeScale, true]
-
A.
hasLargeScale
chosen
Indicates that an entity operates, exists, or is implemented at a large or extensive scale relative to typical or baseline cases.
-
B.
isSmallScale
Indicates that the related activity, operation, or entity occurs on a limited or minor scale, involving relatively small size, scope, or capacity.
-
C.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
D.
isPartOfLargeScaleStructure
Indicates that an entity is a component or constituent of a larger, overarching structure or system.
-
E.
hasLargeScaleStructure
Indicates that an entity possesses or exhibits a large-scale structural organization or pattern, typically extending over substantial spatial or conceptual extents.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a508b0c4819082fbcc27d559ea2f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.