Triple
T4510749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haverford College |
E102046
|
entity |
| Predicate | honorCodeScope |
P6976
|
FINISHED |
| Object | academic integrity |
—
|
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 integrity | Statement: [Haverford College, honorCodeScope, academic integrity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorCodeScope Context triple: [Haverford College, honorCodeScope, academic integrity]
-
A.
certificationScope
Indicates the specific range, domain, or subject matter that a given certification covers or applies to.
-
B.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
C.
organizationalScope
chosen
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
-
D.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5712b9308190876c117b50d12635 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.