Triple

T19047917
Position Surface form Disambiguated ID Type / Status
Subject Phoenix Project E466181 entity
Predicate significantScale P134879 FINISHED
Object large-scale 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: large-scale | Statement: [Phoenix Project, significantScale, large-scale]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantScale
Context triple: [Phoenix Project, significantScale, large-scale]
  • A. significantPort
    Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
  • B. significantAfter
    Indicates that one event or state occurs after another in a way that is temporally meaningful or non-trivially later, not just immediately or insignificantly afterward.
  • C. significantUnit
    Indicates that one unit is considered especially important, primary, or relevant in relation to another entity or context.
  • D. significantMedium
    Indicates that a medium (such as a material, format, or channel) plays an important or defining role in the way an entity is created, expressed, or communicated.
  • E. typeOfSignificance
    Indicates that one entity specifies the nature or category of importance, relevance, or significance that another entity possesses.
  • 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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d8057dec8190b9f1e0b54084ecec completed April 20, 2026, 7:38 a.m.
PD Predicate disambiguation batch_69e4b99633c8819097988608c278ecf8 completed April 19, 2026, 11:16 a.m.
PDg Predicate description generation batch_69e4c0fc3c4c8190abbfe06e1bd3325c completed April 19, 2026, 11:48 a.m.
Created at: April 10, 2026, 12:03 p.m.