Triple
T31139446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPED |
E793740
|
entity |
| Predicate | hasMultipleExpansions |
P191699
|
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: [CPED, hasMultipleExpansions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleExpansions Context triple: [CPED, hasMultipleExpansions, true]
-
A.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
B.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
C.
expandsIn
Indicates that one entity grows, spreads, or extends its presence or influence within the space, scope, or context defined by another entity.
-
D.
hasExpansiveViews
Indicates that an entity offers wide-ranging, unobstructed, or panoramic views of its surroundings.
-
E.
hasExpansionType
Indicates that an entity is associated with a particular mode or category of expansion (such as how it grows, extends, or scales).
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 29, 2026, 9:05 p.m.