Triple
T490799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carleton College |
E9983
|
entity |
| Predicate | hasHonorCode |
P2815
|
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: [Carleton College, hasHonorCode, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorCode Context triple: [Carleton College, hasHonorCode, yes]
-
A.
hasEthicsDocument
Indicates that an entity possesses or is associated with a formal document outlining ethical principles, guidelines, or policies.
-
B.
honorSystem
chosen
Indicates a relationship where compliance, access, or behavior is governed by trust in individuals to act honestly without direct enforcement or verification.
-
C.
honourSystem
Indicates a relationship where compliance, access, or behavior is governed by trust in individuals to act honestly without direct enforcement or verification.
-
D.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
E.
honoursSystem
Indicates that an entity follows or complies with a particular system of rules, standards, or principles.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e22a308190b04d12974fd08a38 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.