Triple
T25265278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Struma |
E633412
|
entity |
| Predicate | numberOfPeopleOnBoardApprox |
P111137
|
FINISHED |
| Object | around 780 |
—
|
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: around 780 | Statement: [Struma, numberOfPeopleOnBoardApprox, around 780]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPeopleOnBoardApprox Context triple: [Struma, numberOfPeopleOnBoardApprox, around 780]
-
A.
totalPeopleOnBoard
Indicates the total number of people currently present on a given vehicle, vessel, or similar conveyance.
-
B.
passengersCountApproximate
Indicates that the number of passengers involved is given as an approximate or estimated count rather than an exact figure.
-
C.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
D.
crewAndPassengersCount
Indicates the total number of people on a vehicle or vessel, combining both crew members and passengers.
-
E.
hasApproximateNumberOfPeople
chosen
Indicates that an entity is associated with an estimated or approximate count of people, rather than an exact number.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 21, 2026, 1:14 p.m.