Triple
T29468334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavlov A |
E747440
|
entity |
| Predicate | relativeSizeTo |
P8238
|
FINISHED |
| Object | smaller than Pavlov (lunar crater) |
—
|
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: smaller than Pavlov (lunar crater) | Statement: [Pavlov A, relativeSizeTo, smaller than Pavlov (lunar crater)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeTo Context triple: [Pavlov A, relativeSizeTo, smaller than Pavlov (lunar crater)]
-
A.
hasRelativeSize
chosen
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
B.
relativeSizeOnTethys
Indicates how the size of one entity compares to another specifically in the context of Tethys.
-
C.
relativeSizeWithinSite
Indicates the comparative size relationship of one entity to another within the same site or local context.
-
D.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
E.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
Created at: April 28, 2026, 3:55 p.m.