Triple
T31174276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Φ |
E794697
|
entity |
| Predicate | usedInOrganizationNames |
P32965
|
FINISHED |
| Object | academic honor societies |
—
|
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: academic honor societies | Statement: [Φ, usedInOrganizationNames, academic honor societies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOrganizationNames Context triple: [Φ, usedInOrganizationNames, academic honor societies]
-
A.
usedInOrganization
Indicates that something (such as a tool, method, or resource) is employed or applied within a particular organization.
-
B.
usedInFullNameOf
chosen
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
C.
usesOrganization
Indicates that one entity makes use of, relies on, or operates through a particular organization to perform its functions or activities.
-
D.
hasNameInOrganization
Indicates that an entity is known by a particular name within the context of a specific organization.
-
E.
namedForOrganization
Indicates that one entity bears a name that is derived from or given in honor of a particular organization.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 9:07 p.m.