Triple
T17290413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Seals |
E419767
|
entity |
| Predicate | functionInCommunity |
P108949
|
FINISHED |
| Object | mark identity of the elect |
—
|
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: mark identity of the elect | Statement: [Three Seals, functionInCommunity, mark identity of the elect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInCommunity Context triple: [Three Seals, functionInCommunity, mark identity of the elect]
-
A.
hasCommunityFunction
chosen
Indicates that an entity serves or provides a function, role, or service that benefits or supports a community.
-
B.
formsCommunityIn
Indicates that an entity comes together with others to establish or participate in a community within a particular context or location.
-
C.
communityAspect
Indicates that something pertains to, reflects, or influences the communal or social dimension of a group or community.
-
D.
collaboratingCommunity
Indicates that two or more entities are actively working together toward shared goals or projects as part of a community relationship.
-
E.
usedInCommunity
Indicates that something is employed, practiced, or applied within a particular community or communal context.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e437837d048190949b947f5437636d |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.