Triple
T19294524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regent University School of Law |
E482526
|
entity |
| Predicate | hasMottoFocus |
P56183
|
FINISHED |
| Object | Christian leadership |
—
|
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: Christian leadership | Statement: [Regent University School of Law, hasMottoFocus, Christian leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoFocus Context triple: [Regent University School of Law, hasMottoFocus, Christian leadership]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoContext
chosen
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
C.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
E.
hasMottoAuthority
Indicates that an entity has the official power or right to establish, approve, or oversee the use of a motto for another entity.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc84500c81908ac53711335ad2d9 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.