Triple
T6326339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AUB campus botanical collection |
E141871
|
entity |
| Predicate | isResourceFor |
P70057
|
FINISHED |
| Object | AUB students |
—
|
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: AUB students | Statement: [AUB campus botanical collection, isResourceFor, AUB students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResourceFor Context triple: [AUB campus botanical collection, isResourceFor, AUB students]
-
A.
hasTypeOfResource
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
B.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
C.
isAuthorityFor
Indicates that one entity holds recognized power, control, or decision-making responsibility over another entity or domain.
-
D.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
E.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e833a0819096000b47e776949d |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:29 p.m.