Triple
T30720449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP |
E782141
|
entity |
| Predicate | multilinkExtension |
P96689
|
FINISHED |
| Object | Multilink PPP (MLPPP) |
—
|
NE NERFINISHED |
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: Multilink PPP (MLPPP) | Statement: [PPP, multilinkExtension, Multilink PPP (MLPPP)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multilinkExtension Context triple: [PPP, multilinkExtension, Multilink PPP (MLPPP)]
-
A.
extensionType
chosen
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
B.
extensionMechanism
Indicates that one entity provides a way to extend, customize, or add new functionality or components to another entity.
-
C.
extensionTerminus
Indicates the endpoint or final limit to which something is extended or continues.
-
D.
networkExtensible
Indicates that a network can be expanded, upgraded, or adapted to support additional components, capacity, or functionality without fundamental redesign.
-
E.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c592f388190ba1a9fe105624fd7 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.