Triple
T12892646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Functional Requirements for Authority Data |
E308405
|
entity |
| Predicate | concernsEntityType |
P90180
|
FINISHED |
| Object | persons |
—
|
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: persons | Statement: [Functional Requirements for Authority Data, concernsEntityType, persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsEntityType Context triple: [Functional Requirements for Authority Data, concernsEntityType, persons]
-
A.
concernsEntity
chosen
Indicates that something (such as an action, issue, or piece of information) is about or relevant to a particular entity.
-
B.
includedEntityType
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
C.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
-
D.
concernsDomain
Indicates that something (such as an action, statement, or item) is about, relates to, or is focused on a particular domain or field.
-
E.
concernsBusinessType
Indicates that something is related or applicable to a particular type or category of business.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971484aa08190a8adfafabe600903 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.