Triple
T890901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trussville, Alabama |
E19234
|
entity |
| Predicate | mottoReputation |
P20754
|
FINISHED |
| Object | family-oriented community |
—
|
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: family-oriented community | Statement: [Trussville, Alabama, mottoReputation, family-oriented community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoReputation Context triple: [Trussville, Alabama, mottoReputation, family-oriented community]
-
A.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
B.
mottoStatus
Indicates the current state or classification of a motto, such as whether it is official, proposed, historical, or otherwise designated.
-
C.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
mottoStyle
Indicates the stylistic form or presentation in which a motto is expressed.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad019e448190ab991e85dc6d7708 |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4a38ec8190915916d80299ab55 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.