Triple
T28701130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armada de Molucca |
E729552
|
entity |
| Predicate | approximateCrewSizeAtStart |
P883
|
FINISHED |
| Object | about 270 |
—
|
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: about 270 | Statement: [Armada de Molucca, approximateCrewSizeAtStart, about 270]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCrewSizeAtStart Context triple: [Armada de Molucca, approximateCrewSizeAtStart, about 270]
-
A.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
B.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
C.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
D.
hasCrewReductionComparedTo
Indicates that one entity operates with a smaller crew size compared to another entity.
-
E.
memberCountAtFounding
Indicates the number of members an entity had at the time it was founded.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 28, 2026, 5:42 a.m.