Triple
T9088896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Métro line 12 |
E217827
|
entity |
| Predicate | integrationIntoCMPNetwork |
P15157
|
FINISHED |
| Object | 1931 |
—
|
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: 1931 | Statement: [Paris Métro line 12, integrationIntoCMPNetwork, 1931]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationIntoCMPNetwork Context triple: [Paris Métro line 12, integrationIntoCMPNetwork, 1931]
-
A.
integrationContext
Indicates the contextual framework or environment within which multiple components, systems, or processes are combined and interact as an integrated whole.
-
B.
integrationProperty
Indicates a relationship where one entity serves as a property, parameter, or configuration aspect governing how another entity is integrated or combined with systems, components, or processes.
-
C.
partOfNetworkExpansion
Indicates that an entity participates in or contributes to the growth or extension of a larger network.
-
D.
integratedIn
chosen
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
E.
integratesCapability
Indicates that one entity incorporates or combines another entity’s capability into its own functionality.
- 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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9657d48081909e0ae0f1fa8ff599 |
completed | April 1, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:14 p.m.