Triple
T150769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governing Body of Harrow School |
E3425
|
entity |
| Predicate | meetsFor |
P1220
|
FINISHED |
| Object | strategic decision-making |
—
|
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: strategic decision-making | Statement: [Governing Body of Harrow School, meetsFor, strategic decision-making]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsFor Context triple: [Governing Body of Harrow School, meetsFor, strategic decision-making]
-
A.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
B.
meets
chosen
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
C.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
D.
meetsDuring
Indicates that one entity encounters or comes together with another while a specified event or time interval is in progress.
-
E.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580dda148190a522e0ac276d5f33 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.