Triple
T28050415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ming treasure fleet |
E708803
|
entity |
| Predicate | estimatedNumberOfShips |
P39920
|
FINISHED |
| Object | over 200 ships on some voyages |
—
|
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: over 200 ships on some voyages | Statement: [Ming treasure fleet, estimatedNumberOfShips, over 200 ships on some voyages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedNumberOfShips Context triple: [Ming treasure fleet, estimatedNumberOfShips, over 200 ships on some voyages]
-
A.
numberOfShips
chosen
Indicates the quantity of ships associated with a given entity or situation.
-
B.
typicalPassengerCapacityPerShip
Indicates the usual number of passengers that a ship of a given type or class is designed or expected to carry.
-
C.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
D.
classShipCount
Indicates the number of ships associated with a particular class or category.
-
E.
numberOfPlannedShips
Indicates the total count of ships that are intended or scheduled to be built, deployed, or used according to a plan.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 8:32 p.m.