Triple
T28136319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florus |
E714215
|
entity |
| Predicate | workIncludesAccountOf |
P16326
|
FINISHED |
| Object | Third Servile War |
—
|
NE NERFINISHED |
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: Third Servile War | Statement: [Florus, workIncludesAccountOf, Third Servile War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workIncludesAccountOf Context triple: [Florus, workIncludesAccountOf, Third Servile War]
-
A.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
-
B.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
C.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
D.
containsAccountOf
chosen
Indicates that one entity includes, records, or holds information about another entity’s account.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:50 p.m.