Triple
T1132551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davidson College |
E23063
|
entity |
| Predicate | meetsFullNeed |
P4233
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Davidson College, meetsFullNeed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsFullNeed Context triple: [Davidson College, meetsFullNeed, yes]
-
A.
meets
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
B.
meetsEvery
Indicates that one entity encounters or comes into contact with every member of a specified set of entities.
-
C.
meetsUnder
Indicates that one entity encounters or comes together with another entity in a context where it is subordinate to, governed by, or occurring within the scope or authority of a third entity or condition.
-
D.
meetsFollowing
Indicates that one entity encounters or comes together with another entity that appears or occurs later in a given sequence or order.
-
E.
satisfies
chosen
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.