Triple
T35569493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camerinus |
E1027870
|
entity |
| Predicate | usedByStatus |
P65653
|
FINISHED |
| Object | Roman aristocracy |
—
|
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: Roman aristocracy | Statement: [Camerinus, usedByStatus, Roman aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByStatus Context triple: [Camerinus, usedByStatus, Roman aristocracy]
-
A.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
B.
usageStatus
chosen
Indicates the current state or condition of how something is being used, such as whether it is active, inactive, available, or in use.
-
C.
usedByUntil
Indicates that one entity makes use of another entity up to, but not beyond, a specified point in time.
-
D.
usedByLabel
Indicates that something serves as a label or identifier that is utilized by another entity.
-
E.
usedByGroup
Indicates that something is utilized or employed by a particular group or collective 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:04 p.m.