Triple
T18515681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centro Escolar University Makati |
E452454
|
entity |
| Predicate | isInIndustry |
P19086
|
FINISHED |
| Object | higher education |
—
|
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: higher education | Statement: [Centro Escolar University Makati, isInIndustry, higher education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInIndustry Context triple: [Centro Escolar University Makati, isInIndustry, higher education]
-
A.
isPartOfIndustry
chosen
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
B.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
C.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
D.
hasIndustryRole
Indicates that an entity holds or performs a specific role, function, or position within a particular industry or sector.
-
E.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338a628c81909db08ae7dc94f59a |
completed | April 19, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.